Hi guys, we have a customer with quite a lot of users which is running FSLogix profiles. The VHDX disks are around 10-18GB/32 on average. I noticed that the recycle bin has a limit of 8GB and if I'm not wrong the storage sense removes files from the recycle bin per default if they are older than 30 days. Not sure if I can optimize anything with the recycle bin or if I should leave it as is, but I was thinking of running a logon script that sets the limit to 2GB or change the storage sense policy to 7 days instead. Another thing is that I'm thinking of adding the following exclusions to their XML, what do you guys think? I don't want to complicate the environment, just optimize their FSLogix setup, thats all. <!-- New Teams (MSIX) WebView2 Cache --> Exclude Copy="0"AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\Cache/Exclude Exclude Copy="0"AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\Code Cache/Exclude Exclude Copy="0"AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\GPUCache/Exclude Exclude Copy="0"AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\Service Worker\CacheStorage/Exclude Exclude Copy="0"AppData\Local\Packages\MSTeams_8wekyb3d8bbwe\LocalCache\Microsoft\MSTeams\EBWebView\WV2Profile_tfw\WebStorage\2\CacheStorage/Exclude <!-- Chrome Optimization Guide AI Model --> Exclude Copy="0"AppData\Local\Google\Chrome\User Data\OptGuideOnDeviceModel/Exclude

I don't add anything to the XML file unless it is a desperate situation. What is your rationale for doing so?

Hey James! Well the main reason is because their fileshare that hosts the profiles is now almost 30TB and they are getting to a point where they have to increase the physical storage. I know that FSLogix profiles are ment to be large. Just trying to see if I can save a few TBs and then after that they will have to get more storage...

Well whatever you exclude just caches out to local disk anyway, so you just swap storage for I/O. If storage is becoming a problem, I'd switch them to something else. You're right, containers are meant to be huge. I'd adopt a pruning script before I started excluding stuff in the XML file - that XML file was only meant for emergencies https://github.com/aaronparker/fslogix/tree/main/Profile-Cleanup.

thank you James, I Will check it out and test it!

I'm with James, i rarely add anything to the XML. I want this profile treated like a normal persistent local profile. Usually the biggest culprit is the OST file from Outlook cached mode. I'd do some more investigation in multiple different profiles and see where majority of the size is coming from.

Hey Steve, thanks! Yeah teams is taking up around 2-4GB in each profile as far as I can see. Thus my suggestion on the exclusion is XML. However, I start to notice that this might not be the best idea. Is that because an exclusion can mess up the profile or teams in this case for old/new users?

That exclusions XML was included as a feature for emergencies only. The idea with FSLogix is that your ENTIRE profile is maintained. When you exclude stuff it just gets written to a local folder instead and then dropped. Everything you exclude will then re-cache during your session, every time. A pruning script to delete old entries should be a better option, really. That way some of the cache is maintained rather than dropping it at every logoff.

Sounds really good. What about the recycle bin for example? I see that users that have 8GB in their recycle bin have 18GB profiles instead of 10GB because those files are not getting removed on a daily basis. I understand that companies would like to give their users the option to keep these files for a while and there should be a default storage sense policy that removes files older than 30 days from the recycle bin but not sure if this actually works out of the box. Do you think that the recycle bin should not be touched at all? or can it be somehow included in the prune script maybe? For now I'm going with that advice of yours James, will get that prune script up and running but I will not add all of that which is included in the xml from that git. I will have to go through a few profiles with treesize and understand what takes place and then add those paths to the xml. They already have the fslogix xml configured so it would make more sense to even remove this and move over to the prune script. I bet the performance will even increase.

Depends on your users. If your users are in the habit of restoring stuff from the Recycle Bin, you may have to keep it. However if you expressly tell them stuff in the Recycle Bin will be deleted at the end of each day, you can get away with not keeping it. If you choose to not save the Recycle Bin, though, I would use the policy to do it instead of the XML file.

you mean the fslogix policy for the recycle bin?

Yes

Don't forget that a User's OST might include Shared Folders in Outlook. We identified that as a huge reason why FSL Profiles were so big, so we set a Policy to prevent that and it helped a lot.

nice one Greg, which policy did you configure for this? you can see these files if you open up the disk right?

Give this a look: https://windowsreport.com/outlook-disable-download-shared-folders-gpo/ I can't remember if you have to Rename the current Profile (when the User is logged out of course) to, like, ".OLD" and let FSL create a new one sans the Shared Folders... Test it with a single User first to find that out...